1. Home
  2. Vulnerabilities
  3. CVE-2023-53276
0.0
NA
CVE-2023-53276
ubifs: Free memory for tmpfile name
Description

In the Linux kernel, the following vulnerability has been resolved: ubifs: Free memory for tmpfile name When opening a ubifs tmpfile on an encrypted directory, function fscrypt_setup_filename allocates memory for the name that is to be stored in the directory entry, but after the name has been copied to the directory entry inode, the memory is not freed. When running kmemleak on it we see that it is registered as a leak. The report below is triggered by a simple program 'tmpfile' just opening a tmpfile: unreferenced object 0xffff88810178f380 (size 32): comm "tmpfile", pid 509, jiffies 4294934744 (age 1524.742s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename ubifs_tmpfile vfs_tmpfile path_openat Free this memory after it has been copied to the inode.

INFO

Published Date :

Sept. 16, 2025, 8:15 a.m.

Last Modified :

Sept. 16, 2025, 12:49 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2023-53276 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
Solution
Free allocated memory for tmpfile names after copying to the inode.
  • Ensure memory allocated for tmpfile names is freed.
  • Verify the fix in the Linux kernel update.
  • Apply kernel updates promptly.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2023-53276.

URL Resource
https://git.kernel.org/stable/c/107d481642c356a5668058066360fc473911e628
https://git.kernel.org/stable/c/1e43d4284bdc3bd34bd770fea13910ac37ab0618
https://git.kernel.org/stable/c/1fb815b38bb31d6af9bd0540b8652a0d6fe6cfd3
https://git.kernel.org/stable/c/29738e1bcc799dd754711d4e4aab967f0c018175
https://git.kernel.org/stable/c/823f554747f8aafaa965fb2f3ae794110ed429ef
https://git.kernel.org/stable/c/8ad8c67a897e68426e85990ebfe0a7d1f71fc79f
https://git.kernel.org/stable/c/b8f444a4fadfb5070ed7e298e0a5ceb4a18014f3
https://git.kernel.org/stable/c/ce840284929b75dbbf062e0ce7fcb78a63b08b5e
https://git.kernel.org/stable/c/fd197308c0e4f738c7ea687d5332035c5753881c
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2023-53276 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2023-53276 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2023-53276 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2023-53276 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Sep. 16, 2025

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: ubifs: Free memory for tmpfile name When opening a ubifs tmpfile on an encrypted directory, function fscrypt_setup_filename allocates memory for the name that is to be stored in the directory entry, but after the name has been copied to the directory entry inode, the memory is not freed. When running kmemleak on it we see that it is registered as a leak. The report below is triggered by a simple program 'tmpfile' just opening a tmpfile: unreferenced object 0xffff88810178f380 (size 32): comm "tmpfile", pid 509, jiffies 4294934744 (age 1524.742s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename ubifs_tmpfile vfs_tmpfile path_openat Free this memory after it has been copied to the inode.
    Added Reference https://git.kernel.org/stable/c/107d481642c356a5668058066360fc473911e628
    Added Reference https://git.kernel.org/stable/c/1e43d4284bdc3bd34bd770fea13910ac37ab0618
    Added Reference https://git.kernel.org/stable/c/1fb815b38bb31d6af9bd0540b8652a0d6fe6cfd3
    Added Reference https://git.kernel.org/stable/c/29738e1bcc799dd754711d4e4aab967f0c018175
    Added Reference https://git.kernel.org/stable/c/823f554747f8aafaa965fb2f3ae794110ed429ef
    Added Reference https://git.kernel.org/stable/c/8ad8c67a897e68426e85990ebfe0a7d1f71fc79f
    Added Reference https://git.kernel.org/stable/c/b8f444a4fadfb5070ed7e298e0a5ceb4a18014f3
    Added Reference https://git.kernel.org/stable/c/ce840284929b75dbbf062e0ce7fcb78a63b08b5e
    Added Reference https://git.kernel.org/stable/c/fd197308c0e4f738c7ea687d5332035c5753881c
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.